Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(ci): add Conventional Commits GitHub Action #3030

Merged
merged 1 commit into from
Jul 29, 2024

Conversation

derekbit
Copy link
Member

Which issue(s) this PR fixes:

Issue longhorn/longhorn#8824

What this PR does / why we need it:

Special notes for your reviewer:

Additional documentation or context

@derekbit derekbit self-assigned this Jul 29, 2024
@derekbit derekbit marked this pull request as draft July 29, 2024 01:28
Longhorn 8824

Signed-off-by: Derek Su <derek.su@suse.com>
@derekbit derekbit requested a review from c3y1huang July 29, 2024 06:08
@derekbit derekbit marked this pull request as ready for review July 29, 2024 06:08
@derekbit derekbit changed the title chore(ci): add "Conventional Commits GitHub Action" chore(ci): add Conventional Commits GitHub Action Jul 29, 2024
@derekbit derekbit merged commit 4346be5 into longhorn:master Jul 29, 2024
7 checks passed
- name: Lint Pull Request
uses: amannn/action-semantic-pull-request@v5.5.3
env:
GITHUB_TOKEN: ${{ secrets.CUSTOM_GITHUB_TOKEN }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CUSTOM_GITHUB_TOKEN has more permissions than the built-in one. Can we just use the built-in token (each action will automatically create a token for the action and delete it after the action is finished) instead?

ref: https://github.com/wagoid/commitlint-github-action#token

build
ci
revert
BREAKING
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For breaking change, we can just use the second format via !.

BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in Semantic Versioning). A BREAKING CHANGE can be part of commits of any type.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After thinking, we can keep this as it's also valid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants